Under normal circumstances, you should not need to configure the behavior of the Managed Change functions. The default settings are adequate for most environments. However, they can be configured to meet specific requirements or for compatibility with customization.
The Managed Change settings are described in the following table.
| Setting | Description |
|---|---|
|
CreateProjectCopyInSelectedFolder |
If set to Y (default), Meridian creates project copies in the project folder that is selected by the user. If customized event procedures attempt to move the document to a different location, folder locking errors can occur if more than one procedure is active at the same time. When set to N (No), the copy is made without any parent folder. Meridian then moves the document to its destination folder as calculated by the Field-Path definition, if it is defined. If the Field-Path definition is not defined, the copy is moved to the folder that is current at the time that the copy is made. |
|
DiscardProjectRefs |
Controls the disposition of references between project copies made in the same project folder when one of the project copies is discarded. The possible values are: 0 – Discard all references (default) 1 – Do not discard references made by the CAD links 2 – Do not discard custom (manual) references 3 – Do not discard any references. Note When set to a value other than 0, references between project copies will be redirected to the master document if one of the project copies is discarded from the project. If the remaining project copy is released from the project, both master documents will then be related by a reference that did not exist prior to the project copies being made. In some scenarios, such as assembly relationships, this might be desirable. In other scenarios, such as custom references, this might not be desirable. Carefully consider and test all scenarios with all available reference types and your business processes before changing this setting in a production environment. |
|
DoNotRerouteRefs2Master |
If set to Y (Yes), incoming references are not rerouted to the master document after a project copy is released. The references remain routed to the inactive project copy. The default is N (No). |
|
RtmRenditionAction |
Controls the disposition of the master document rendition when a project copy is released as a new revision of the master document. The possible values are: 0 - Copy the rendition from the project copy to the master document. This is the default. 1 - Queue the master document in Publisher to regenerate the master document rendition. Use this setting if Publisher is configured to add a watermark to the previous version of the rendition. 2 - Do nothing. This setting is provided for compatibility with custom event handlers that determine what is done. |
To configure the Managed Change settings:
Click the Edit button to modify the settings.
Tip To export the settings file to your computer, click the Export button. This can be useful if you would rather edit the file in your favorite text editor. You can then copy your changes to the Clipboard and paste them into Configurator.
Related concepts